Node / meshtastic / Meshtastic-Android / files / docs / gl-rES / user / node-metrics.md

Displaying Rendered • View raw • Download

title: Node Metrics

parent: User Guide

nav_order: 5

last_updated: 2026-08-30

description: Telemetry dashboards for each mesh node — device health, environment sensors, air quality, signal quality, power, traceroute, and position history.

aliases:

• metrics

• telemetry

• device-metrics

• signal

The node detail screen provides comprehensive telemetry and metrics for each node on your mesh.

1. Navigate to Nodes.

2. Tap the node you want to inspect.

3. Scroll to the Telemetry section and find the category you want — Signal Quality, Device Metrics, Environment Metrics, Air-Quality Metrics, Power Metrics, Position, and the rest.

4. Tap the refresh button on a row to ask the node for a fresh reading. The chart button beside it opens that category's history, and appears once the node has reported that kind of telemetry.

!Node detail — local device

The Position row expands to show location data for nodes that share GPS:

!Position inline content

│ ℹ️ Note: Metrics are only available when they have been reported by the remote node. Metrics

│ update at intervals configured on each node's telemetry settings.

Basic operating information reported by each node:

Device Metrics has no cards on the node detail screen. Use the chart button on its row to open the Device Metrics screen, where battery level, voltage, ChUtil, and AirUtil are plotted over time and every reading — uptime included — is listed with its timestamp underneath. Pick a time frame at the top of the screen, and use the save icon in the app bar to export the visible history as CSV.

│ 💡 Tip: Where a category does show cards — Environment, Air Quality, and Power — touch & hold a

│ card to copy its value to the clipboard. On a chart screen, pinch to zoom the time axis.

Environmental sensor data (requires compatible hardware):

Environment metrics are charted over time — temperature, humidity, and pressure each get their own line chart with the measurement unit displayed on the Y axis.

The BME680 IAQ (Indoor Air Quality) index is a single 0–500+ value derived from gas resistance, shown against a color-coded scale from Excellent to Dangerously Polluted:

!IAQ index scale from Excellent to Dangerously Polluted

│ 💡 Tip: Environment metrics require a sensor connected to the remote node. Not all nodes report

│ environmental data. See Telemetry & │ Sensors

│ for a full list of supported sensors.

Air Quality is a dedicated metrics view for nodes equipped with a particulate-matter and/or CO₂ sensor. It is separate from the BME680 IAQ reading listed under Environment Metrics — IAQ is a single gas-resistance-derived index, while the Air Quality view charts the underlying particulate and CO₂ measurements.

CO₂ readings are color-coded by severity so you can read air quality at a glance:

!Air quality readings with color-coded CO₂ severity

An air-quality log/metrics button appears on the node detail screen only when the node has reported air-quality telemetry. From the Air Quality view you can:

• Select a time frame for the charts.

• Filter with metric chips — only metrics that have data are shown.

• Refresh / request the latest air-quality telemetry.

• Export to CSV for analysis in a spreadsheet.

│ 💡 Tip: Air Quality metrics require a compatible air-quality sensor on the remote node. See

│ Telemetry & │ Sensors

│ for supported hardware.

Radio signal quality information:

Signal quality is rated from SNR relative to the active LoRa modem preset's demodulation floor, not from fixed thresholds — a given SNR means different things on different presets (e.g. −15 dB is fine on LongSlow but unusable on ShortFast). RSSI is shown but is not part of the rating. In the table, limit is the preset's SNR limit.

See Understanding the Signal Meter for the full explanation.

Local Stats from your connected radio are also shown in Signal Quality when available. These logs include noise floor, traffic counters, relay counters, online node counts, and radio uptime. The noise floor chart uses a dashed reference line at -85 dBm to help identify a busy RF environment.

• Request — ask the connected radio for a fresh Local Stats telemetry report

• Clear — remove Local Stats logs for that node

• Save — export the visible Local Stats history as CSV

Power management telemetry (requires INA sensor or compatible hardware):

The node detail screen shows cards for channels 1 to 3. Use the chart button on the Power Metrics row to open the chart screen, which lists a chip for every channel that reported data — up to eight — and charts the one you select. Use the label field under the chips to give a channel a name of your own, such as Solar or Battery. The app does not derive a wattage figure from voltage and current.

Traceroute shows the path a message takes through the mesh:

1. From the node detail screen's Telemetry section, tap the refresh button on the Traceroute row. You cannot traceroute your own node, and the button accepts one request every 30 seconds.

2. The app sends a traceroute request to the target node.

3. Results show each hop with its SNR.

A traceroute is a round trip, so each saved result carries a hop count in each direction — Forward Hops and Return Hops — and the Round Trip time in seconds. A result marked Direct reached the target with no relay in between. Tap a result to read the route traced toward the destination and the route traced back to you, with the SNR of every hop. On Android that view offers View on map, which draws the same path, as long as the start and destination nodes have both shared a position.

A result marked No Response means the target never answered. It may be out of range, asleep, or configured not to reply. Wait for the 30-second cooldown to clear and try again; if it keeps failing, send a direct message first to confirm the node is reachable at all.

Historical position data for nodes that share their location:

• GPS coordinates

• Altitude

• Speed (if moving)

• Timestamp for each position report

Shows which nodes a given node can directly hear, useful for understanding mesh topology.

Nodes that run Meshtastic on a Linux host, such as a Raspberry Pi, report the host's own health — free memory, free disk space, one-, five-, and fifteen-minute load averages, and how long the host has been up. The Host Metrics row is always listed; its chart button appears once a node has reported them.

A node running the PAX counter module reports how many Wi-Fi and Bluetooth devices it saw nearby, as a crowd-size estimate, and charts the two counts alongside their total. The PAX Metrics row is always listed; its chart button appears once a node has reported them. The counts are of devices, not people.

• Nodes — node list, filtering, and sorting

• Telemetry & Sensors — supported sensors and configuration

• Signal Meter — how signal quality is calculated from SNR and RSSI

• Local Mesh Discovery — traceroute details and neighbor info

• Units & Locale — temperature, distance, and speed display formats